Skip to content

Conversation

@jatinsu
Copy link

@jatinsu jatinsu commented Jan 27, 2026

The newly introduced OKD feature set should not be enabled on OCP clusters. This PR introduces this and throws an error if a user has the OKD featureset enabled in the install-config and if the installer isn't compiled for scos (TAGS=scos hack/build.sh)

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 27, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 27, 2026

@jatinsu: This pull request references OKD-259 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.22.0" version, but no target version was set.

Details

In response to this:

The newly introduced OKD feature set should not be enabled on OCP clusters. This PR introduces this and throws an error if a user has the OKD featureset enabled in the install-config and if the installer isn't compiled for scos (TAGS=scos hack/build.sh)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from barbacbd and tthvo January 27, 2026 16:21
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tthvo for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

commands I ran:
go get github.com/openshift/api@latest
go get github.com/openshift/client-go@latest
go mod tidy
go mod vendor
This check only allows the OKD featureset to be enabled in the
install-config when the installer is compiled using `TAGS=scos hack/build.sh`
Copy link
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Local testing worked as expected and unit tests also shows that.

$ go test -tags=scos -v -run "TestFeatureGates/OKD_featureset" ./pkg/types/validation/
=== RUN   TestFeatureGates
=== RUN   TestFeatureGates/OKD_featureset_requires_SCOS-compiled_installer
--- PASS: TestFeatureGates (0.00s)
    --- PASS: TestFeatureGates/OKD_featureset_requires_SCOS-compiled_installer (0.00s)
PASS
ok  	github.com/openshift/installer/pkg/types/validation	0.021s

$ go test -v -run "TestFeatureGates/OKD_featureset" ./pkg/types/validation/
=== RUN   TestFeatureGates
=== RUN   TestFeatureGates/OKD_featureset_requires_SCOS-compiled_installer
--- PASS: TestFeatureGates (0.00s)
    --- PASS: TestFeatureGates/OKD_featureset_requires_SCOS-compiled_installer (0.00s)
PASS
ok  	github.com/openshift/installer/pkg/types/validation	0.021s

@tthvo
Copy link
Member

tthvo commented Jan 27, 2026

/cc @patrickdillon

@openshift-ci openshift-ci bot requested a review from patrickdillon January 27, 2026 16:51
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@jatinsu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-custom-dns fccddc3 link false /test e2e-gcp-custom-dns
ci/prow/e2e-gcp-secureboot fccddc3 link false /test e2e-gcp-secureboot
ci/prow/e2e-gcp-ovn-byo-vpc fccddc3 link false /test e2e-gcp-ovn-byo-vpc
ci/prow/e2e-vsphere-ovn fccddc3 link true /test e2e-vsphere-ovn
ci/prow/e2e-metal-assisted fccddc3 link false /test e2e-metal-assisted
ci/prow/e2e-azurestack fccddc3 link false /test e2e-azurestack
ci/prow/e2e-vsphere-ovn-zones fccddc3 link false /test e2e-vsphere-ovn-zones
ci/prow/gcp-custom-endpoints-proxy-wif fccddc3 link false /test gcp-custom-endpoints-proxy-wif
ci/prow/e2e-azure-ovn-shared-vpc fccddc3 link false /test e2e-azure-ovn-shared-vpc
ci/prow/e2e-metal-ipi-ovn-dualstack fccddc3 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/gcp-private fccddc3 link false /test gcp-private
ci/prow/e2e-aws-ovn-heterogeneous fccddc3 link false /test e2e-aws-ovn-heterogeneous
ci/prow/e2e-metal-single-node-live-iso fccddc3 link false /test e2e-metal-single-node-live-iso
ci/prow/e2e-gcp-ovn fccddc3 link true /test e2e-gcp-ovn
ci/prow/e2e-metal-ovn-two-node-fencing fccddc3 link false /test e2e-metal-ovn-two-node-fencing

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jatinsu
Copy link
Author

jatinsu commented Jan 28, 2026

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants